System and method for single page banner integration

ABSTRACT

A dynamic banner may be displayed in a merchant check out page sourced from a merchant server that may be customized to a particular user and/or merchant. The dynamic banner may be provided by a transaction account provider server and may invite the user to select an offer. In response to the user&#39;s interaction with the offer, the characteristics of the merchant check out page may be changed, for example, a product may be discounted, and/or a new transaction account may be issued to the user by the transaction account provider server and used to complete the checkout process via cross document messaging and cross domain scripting. In this manner, the merchant server and the transaction account provider server may interact with a user within a single web page.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a nonprovisional of, and claims priority to, and thebenefit of U.S. Provisional Application No. 62/195,598, entitled “SYSTEMAND METHOD FOR SINGLE PAGE BANNER INTEGRATION,” filed on Jul. 22, 2015,which is hereby incorporated by reference in its entirety.

FIELD

The present disclosure relates to the integration of banners into thirdparty websites.

BACKGROUND

Merchants may desire to integrate banners and/or transaction accountapplication processes into their online shopping cart pages. However,prior solutions involve significant custom coding in order to customizethe merchant shopping cart pages for the banner and/or transactionaccount application process, present significant data securitychallenges, and slow the user experience as the merchant and thetransaction account provider typically communicate through abusiness-to-business backchannel at various steps of the browserinteraction by the user with the merchant page.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter of the present disclosure is particularly pointed outand distinctly claimed in the concluding portion of the specification. Amore complete understanding of the present disclosure, however, may beobtained by referring to the detailed description and claims whenconsidered in connection with the drawing figures, wherein like numeralsdenote like elements.

FIG. 1 illustrates an exemplary cross-domain scripting cross-documentmessaging offer integration system, in accordance with variousembodiments;

FIG. 2 illustrates a banner display method, in accordance with variousembodiments;

FIG. 3 illustrates a customer application method, in accordance withvarious embodiments;

FIG. 4 illustrates a method of instant account number (IAN) to checkoutreturn, in accordance with various embodiments;

FIG. 5 illustrates a banner request status diagram, in accordance withvarious embodiments; and

FIG. 6 illustrates an account information pass back method, inaccordance with various embodiments.

DETAILED DESCRIPTION

The detailed description of various embodiments herein makes referenceto the accompanying drawings and pictures, which show variousembodiments by way of illustration. While these various embodiments aredescribed in sufficient detail to enable those skilled in the art topractice the disclosure, it should be understood that other embodimentsmay be realized and that logical and mechanical changes may be madewithout departing from the spirit and scope of the disclosure. Thus, thedetailed description herein is presented for purposes of illustrationonly and not of limitation. For example, the steps recited in any of themethod or process descriptions may be executed in any order and are notlimited to the order presented. Moreover, any of the functions or stepsmay be outsourced to or performed by one or more third parties.Furthermore, any reference to singular includes plural embodiments, andany reference to more than one component may include a singularembodiment.

Transaction account providers and merchants may desire to engagetogether as distribution and/or cobrand partners having an integratedonline digital acquisition process leveraged to create a streamlinedacquisition stream for transaction account applicants using merchantupfunnel shopping flows and shopping cart applications. By implementingcross domain scripting and cross document messaging, the digitalacquisition process may be integrated to the upfunnel shopping andshopping cart experience and yet involve minimal upfunnel and cartcustomization by the merchant. For instance, a merchant may integratethe digital acquisition process into the upfunnel shopping and shoppingcart experience within mere hours of coding and related integrationwork, versus previous efforts which required extensive and challengingcoding and integration efforts to develop. As mentioned, merchants maydesire to integrate banners and/or transaction account applicationprocesses into their online shopping cart pages. However, priorsolutions may often involve prohibitively lengthy development effortsfor which the merchant often lacks the time or resources to implement.Importantly, systems and methods are presented herein which provide forstrikingly less resource intensive development commitments frommerchants, all the while providing strong security features and aresponsive user experience.

Also, in this manner, scalability may be enhanced and page reloads maybe minimized. For instance, a banner may be placed within a merchant's“checkout journey” (e.g., the process whereby a user selects andultimately purchases items from the merchant). Integrated customer datamay be exchanged between the user and merchant, the user and transactionaccount provider, and the merchant and transaction account provider.Integrated customer data may comprise data pre-filled into forms of themerchant and/or the transaction account provider based on datapreviously provided to the other. Integrated data may also compriseaccount details, such as where a transaction account application processmay be incorporated into the checkout process whereby a user may applyfor, receive, and use a transaction account for the checkouttransaction, and whereby the transaction account provider may providecontextually relevant incentives. For example, the transaction accountprovider may display a discounted total of the checkout sum associatedwith a transaction account application such as a price reduction,display a reward points sum, and/or display an upsell or related productoffer based on prior transaction histories. More specifically, a bannerplaced in the checkout journey may exchange integrated customer data,and upon a user clicking the banner, open a modal window on top of themerchant parent window, where a credit or charge card application may becompleted and instantly decisioned. In accordance with variousembodiments, modal windows may comprise various types of windows. Forinstance, while iFrames are discussed throughout, in variousembodiments, a browser window, a browser tab, and/or the like may beimplemented. Moreover, such interaction may proceed without (or withminimal) business-to-business integration. Rather, all the assetsstarting with the banner and ending with the conclusion of the checkoutjourney may be hosted exclusively by the transaction account provider,and yet displayed properly integrated with the merchant shopping cartexperience by virtue of the implemented cross domain scripting, wherebymerchant cart customization may be minimized. By virtue of theimplemented cross document messaging, window reloads upon data exchangemay be reduced and/or eliminated.

In accordance with various embodiments, the systems and methodsdisclosed herein securely integrate consumer (e.g., card member)acquisition by the transaction account provider as an experience withinan upfunnel shopping and/or checkout journey of a merchant. Personallyidentifiable information (PII) may be autofilled into documents of thetransaction account provider and/or the merchant. The population of thedocuments may be in real time, or substantially real time. Moreover, thereal time or substantially real time approval and issuance of atransaction account by the transaction account provider to the user maybe supplemented by card account pass back to the merchant checkoutjourney for immediate (or expedited) payment. Furthermore, banners(e.g., prescreened offer requests) may be presented based on the PII. Byvirtue of cross domain scripting and cross document messaging, sharingof certificates between the transaction account provider and themerchant may be avoided or minimized, thus improving the efficiency ofthe interaction. Similarly, account information HTTPS form post andhandover of PII from the transaction account provider to the merchantmay also be avoided or minimized. In this manner, account informationmay pass back from the transaction account provider to the merchant, andPII may pass from the merchant to the transaction account providerwithout the need for sharing of certificates (or with reduced sharing ofcertificates).

As will be discussed further herein, various processes and systemsinvolve the exchange of sensitive information, such as personallyidentifying information, transaction account numbers, and/or the like.For instance, as part of an onboarding process, a merchant may share aCA-signed public SSL certificate which was installed within atrust-store of a transaction account company application server. Themerchant may also specify the domain of their shopping cart experience,and/or payment pages in which transaction account company hosted banners(e.g., dynamic banner JavaScript banners) will be sourced. Thetransaction account company may have assigned a merchant-id to themerchant, such that the merchant is identified. Moreover, furthersecurity may be implemented, such as digital signature signing andverification based on the PKI and Public Key cryptography, as well assecured RESTful Service over HTTPS POST via transaction account companyhosted JavaScript. Furthermore, white list domain validation may beapplied against the domain of the shopping cart experience and/orpayment pages. Furthermore, the payment page may be an HTTPS page, andnot an HTTP page. Time-constraint, single-use security tokens for eachbanner request may be implemented as well as secure HTML5 cross documentmessaging and PKI/AES encrypted instant account number (IAN)information. Finally, the transaction account company hosted aspects mayensure that IAN information is returned only once to the originalmerchant page identified previously in the merchant's checkout journey,and subject to user consent.

With reference to FIG. 1, a cross-domain scripting cross-documentmessaging offer integration system 1 (CDS-CDM integration system 1) maycomprise a transaction account provider server 2 and a merchant server6. A web browser 4 may communicate with both the transaction accountprovider server 2 and the merchant server 6. In this manner, a bannermay be sourced from a transaction account provider server 2 andintegrated into a shopping cart experience (sourced from a merchantserver 6), which is displayed inside a web browser 4. As such, thetransaction account provider server 2 and the merchant server 6 may notbe in direct communication. However, the web browser 4 may accesstransaction account provider resources hosted on the transaction accountprovider server 2 via a transaction account provider resource connection10, and the web browser 4 may access merchant resources hosted on themerchant server 6 via a merchant resource connection 12, so that the webbrowser 4 may create a logical server intermediation connection 8. Dataentered by a user via the web browser 4 may be cross-populated to boththe transaction account provider server 2 and the merchant server 6.Data retrieved individually from the transaction account provider server2 and the merchant server 6 may be securely passed to the other of thetransaction account provider server 2 and the merchant server 6.

Having discussed a CDS-CDM integration system 1, various methods andprocesses may be implemented by various aspects of the CDS-CDMintegration system 1. For example, with reference to FIG. 2, a bannerdisplay method 100 is disclosed. The banner display method 100 mayinvolve various interoperations between a web browser 4 and a merchantserver 6, and between a web browser 4 and a transaction account providerserver 2. For example, a web browser 4 may receive a navigation commanddirecting the web browser 4 to navigate to a merchant check out page(e.g., shopping cart experience/merchant checkout journey) (step 102).In response, the merchant server 6 may prepare a checkout webpage, forinstance, a JSP/ASP webpage. This may comprise, for example, creating adigital signature by signing on the current timestamp using themerchant's SSL certificate private key. Moreover, this may involvesetting up personally identifiable information (PII) receiver fields ofthe merchant check out page in preparation for the collection ofpersonally identifiable information (PII) from the user via the webbrowser 4 (step 104).

After preparing the checkout webpage, the merchant server 6 may servethe checkout webpage to the web browser 4. The served webpage mayinclude the merchant-id, the digital signature, PII, a banner request IDthat uniquely identifies a request for banner to be placed on thewebpage, a time stamp, a placeholder for placement of a banner, and/orbanner sourcing JavaScript (collectively, “returned webpage content”)(step 106).

Upon loading of the checkout page, a secured CORS HTTPS RESTful servicecall is instantiated from the web browser 4 including at least a portionof the returned webpage content. For instance, the portion of returnedwebpage content may include a portion to get a dynamic checkout bannerfor display by the web browser 4 (Step 108). The transaction accountprovider server 2 may be configured to receive the secured CORS HTTPSRESTful service call.

The transaction account provider server 2 may take various actions inresponse to the CORS HTTPS RESTful service call. For instance, thetransaction account provider server 2 may validate and verify aspects ofthe service call, for instance, a portion of the returned webpagecontent. For instance, the transaction account provider server 2 mayvalidate and verify the originating domain of returned webpage content,the merchants digital signature, the banner request ID, the time stampagainst a time limit constraint, and/or the like (Step 110).

In response to the validation and verification step being satisfied, thetransaction account provider server 2 may prepare a dynamic bannercomprising one or more of a secure banner token with an expiration date,a secure URL linked to a portion of the banner (e.g., an “APPLY NOW”button whereby a user may apply for a transaction account of thetransaction account provider), and/or a modal window, such as an iFramefor subsequent hosting of a landing page URL, such as in response to auser interaction with the banner such as clicking an “APPLY NOW” button(Step 112). In various embodiments, a browser tab and/or browser window(such as in addition to the iFrame or in lieu of an iFrame, may becontemplated).

Subsequently, the transaction account provider server 2 may return tothe web browser 4 the created banner, and/or the banner request ID, abanner request status, a secure banner token, and a landing page URL forhosting in the iFrame (Step 114).

Thus, one may appreciate that in loading the page having featuresderived from both the merchant server 6 and the transaction accountprovider server 2, the web browser 4 accesses both servers, whereasneither server communicates directly with the other, nor must the pagebe refreshed to effectuate the transfer of data via the web browser 4among the two servers 2 and 6. Rather, a seamless (or near seamless)user experience manifests, wherein the browser loads a website withcontent from the merchant server 6 and a banner from the transactionaccount provider server 2, and with particular information from one orthe other server made available to the counterpart server and/or pagestherefrom, by virtue of cross-document scripting and cross domainmessaging as disclosed herein. Moreover, one will appreciate that thebanner may be dynamic for different users or different merchants and thebanner is secured against being moved to another website.

With reference to FIG. 3, a customer application method 200 isdisclosed. For instance, as discussed with reference to step 112 above,a banner may invite a user-banner interaction, such as clicking an“APPLY NOW” button. A customer application method 200 may be launched inresponse to a user-banner interaction. For instance, in variousembodiments a customer may click an “APPLY NOW” button (step 202)presented in a banner in a web browser 4 (step 202). The web browser 4may request that the transaction account provider server 2 open alanding page within the iFrame, for instance a banner response offerwhich may include an offer to apply for a transaction account. Thisrequest may be subject to various security checks, such as may beassociated with a secure banner token (step 204). For instance, step 204may more specifically include wherein the transaction account providerserver 2 may validate and verify the request, for instance, thecredit-card provider may validate and verify the secure URL linked to aportion of the banner corresponding to the user-banner interactionand/or the secure banner token with an expiration date of the dynamicbanner (step 205). In response to successful validating and verifying,the transaction account provider server 2 may return and open thelanding page within the iFrame (step 206). As such, step 205 and 206 maybe considered sub-steps of step 204.

Within the web browser 4, landing and/or application pages displayed inthe iFrame may be displayed and the banner request status may be updatedto indicate this display (Step 208). Consequently, the user may interactfurther with the content within the iFrame, such as by applying for atransaction account. The user may exit the page(s) displayed in theiFrame (Step 210). In response to the user exiting the page(s), thecontent provided within the iFrame from the transaction account providerserver 2 may send a cross document message to the content provided fromthe merchant the web browser 4 may send cross document message(s) to atleast one of the merchant check out page provided from the merchantserver 6 and/or to the merchant server 6 and/or updating the bannerrequest status (Step 212). In response, the merchant check out pageprovided from the merchant server 6 may close the iFrame (Step 214).

In various embodiments the content provided within the iFrame from thetransaction account provider server 2 may include an IAN. The IAN may besent via a cross document message to at least one of the merchantcheckout page provided from the merchant server 6 and/or the merchantserver 6, as mentioned. As such, with reference to FIG. 4, a method ofIAN to checkout return 300 may comprise various steps discussed furtherherein below. For instance, as mentioned, within the web browser 4, theuser may complete a transaction account application, with the IANdetails displayed in the iFrame (step 302).

The IAN may be provided from the transaction account provider server 2to the web browser 4 in a format that comprises an encrypted variableencrypted using the merchant's public key in a hidden variable of thedisplayed webpage displayed in the web browser 4. The user may furtheragree to have the IAN returned to the merchant page for forwarding to amerchant server 6 for immediate use in completing a proposed transaction(Step 304). The customer may exit the IAN page displayed in the iFrameand that page may send a banner request id, a banner request status,and/or encrypted IAN JSON object to the merchant server 6 for decryptionvia an AJAX call (Step 306). The merchant server 6 may decrypt the IANusing the merchant's private key (Step 308). Subsequently, the merchantserver 6 may return the decrypted IAN details and pre-fill the purchasepayment information into the shopping cart experience of the web browser4 (step 310).

In various embodiments, the return of the provision of the IAN from thetransaction account provider server 2 to the web browser 4 and then thepre-filling of the purchase payment information and/or decrypted IANdetails into the shopping cart experience of the merchant server 6 asdepicted in the web browser 4 may involve various other aspects. Forinstance, with reference to FIG. 6, an account information pass backmethod 600 is depicted. For instance, an iframe acquisition journey 601may begin with encryption and signature of customer and account detailswith merchant's RSA public key and placement on the page displayed inthe iframe, such as in step 302 (step 602). This page may be displayedto a user in the web browser 4, for instance, in a modal window, such asan iFrame of the web browser 4 (step 603). Moreover, in variousembodiments, the page may be displayed in a browser tab or browserwindow.

In response to the user selecting to activate a return-to-merchantaspect of the page (step 604), such as clicking a button to return to amerchant's shopping cart, the web browser 4 may evaluate whether a boxauthorizing the pre-fill the transaction information with the IANdetails is checked (step 605). If the pre-fill is not authorized,control may be returned to the merchant's shopping cart by thetransmission of a cross document message to close the iFrame (step 607).If the pre-fill is authorized, the encrypted IAN and customer data maybe posted to the merchant's shopping cart by the transmission of a crossdocument message (step 606).

In various instances throughout, the banner request status is discussed,such as with reference to the banner request status being changed.Accordingly, a banner may have different banner request statuses over abanner request lifecycle. For instance, with reference to FIG. 5 as abanner request status diagram 500 may have a shown (S) status 502, or aincompleted (I) status 503, or an approved (A) status 504, or a pending(P) status 505, or a suppressed (R) status 506, or a minimum spendingthreshold reached (T) status 507, or an authentication failed (F) status508, or an IAN passed back (B) status 509. The status may change inresponse to various steps of various methods. For instance, a banner orportion of banner specific to a merchant other than the merchantassociated with the merchant server 6 may be suppressed (R status 506).A banner may not be displayed if a minimum spending threshold (T) 507 isnot reached, for instance, if the banner were to promote a discountgreater than the amount to be spent. A banner may be shown 502, but thebanner may immediately be expired upon the failure of any of theauthentication or security features (F) 508 disclosed herein.

A banner request status may be incomplete (I) 503 in response to a userclicking a shown banner. A banner request status may be pending 505 inresponse to an IAN provisioning decision being in progress. The statusmay be approved (A) in response to an IAN provisioning decision beingapproved. An IAN passed back status (B) 509 may be set in response tothe encrypted IAN being posted to the merchant's shopping cart by thetransmission of a cross document message (see step 606; FIG. 5).

As used herein, the term “network” includes any cloud, cloud computingsystem or electronic communications system or method which incorporateshardware and/or software components. Communication among the parties maybe accomplished through any suitable communication channels, such as,for example, a telephone network, an extranet, an intranet, Internet,point of interaction device (point of sale device, personal digitalassistant (e.g., iPhone®, Palm Pilot®, Blackberry®), cellular phone,kiosk, etc.), online communications, satellite communications, off-linecommunications, wireless communications, transponder communications,local area network (LAN), wide area network (WAN), virtual privatenetwork (VPN), networked or linked devices, keyboard, mouse and/or anysuitable communication or data input modality. Moreover, although thesystem is frequently described herein as being implemented with TCP/IPcommunications protocols, the system may also be implemented using IPX,Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH),or any number of existing or future protocols. If the network is in thenature of a public network, such as the Internet, it may be advantageousto presume the network to be insecure and open to eavesdroppers.Specific information related to the protocols, standards, andapplication software utilized in connection with the Internet isgenerally known to those skilled in the art and, as such, need not bedetailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS ANDPROTOCOLS (1998); JAVA 2 COMPLETE, various authors, (Sybex 1999);DEBORAH RAY AND ERIC RAY, MASTERING HTML 4.0 (1997); and LOSHIN, TCP/IPCLEARLY EXPLAINED (1997) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THEDEFINITIVE GUIDE (2002), the contents of which are hereby incorporatedby reference.

A network may be unsecure. Thus, communication over the network mayutilize data encryption. Encryption may be performed by way of any ofthe techniques now available in the art or which may becomeavailable—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI,GPG (GnuPG), and symmetric and asymmetric cryptosystems.

Phrases and terms similar to “internal data” may include any data acredit issuer possesses or acquires pertaining to a particular consumer.Internal data may be gathered before, during, or after a relationshipbetween the credit issuer and the transaction account holder (e.g., theconsumer or buyer). Such data may include consumer demographic data.Consumer demographic data includes any data pertaining to a consumer.Consumer demographic data may include consumer name, address, telephonenumber, email address, employer and social security number. Consumertransactional data is any data pertaining to the particular transactionsin which a consumer engages during any given time period. Consumertransactional data may include, for example, transaction amount,transaction time, transaction vendor/merchant, and transactionvendor/merchant location. Transaction vendor/merchant location maycontain a high degree of specificity to a vendor/merchant. For example,transaction vendor/merchant location may include a particular gasolinefiling station in a particular postal code located at a particular crosssection or address. Also, for example, transaction vendor/merchantlocation may include a particular web address, such as a UniformResource Locator (“URL”), an email address and/or an Internet Protocol(“IP”) address for a vendor/merchant. Transaction vendor/merchant andtransaction vendor/merchant location may be associated with a particularconsumer and further associated with sets of consumers. Consumer paymentdata includes any data pertaining to a consumer's history of paying debtobligations. Consumer payment data may include consumer payment dates,payment amounts, balance amount, and credit limit. Internal data mayfurther comprise records of consumer service calls, complaints, requestsfor credit line increases, questions, and comments. A record of aconsumer service call includes, for example, date of call, reason forcall, and any transcript or summary of the actual call.

Any communication, transmission and/or channel discussed herein mayinclude any system or method for delivering content (e.g. data,information, metadata, etc.), and/or the content itself. The content maybe presented in any form or medium, and in various embodiments, thecontent may be delivered electronically and/or capable of beingpresented electronically. For example, a channel may comprise a websiteor device (e.g., Facebook, YouTube®, AppleTV®, Pandora®, xBox®, Sony®Playstation®), a uniform resource locator (“URL”), a document (e.g., aMicrosoft Word® document, a Microsoft Excel® document, an Adobe .pdfdocument, etc.), an “ebook,” an “emagazine,” an application ormicroapplication (as described herein), an SMS or other type of textmessage, an email, Facebook, twitter, MMS and/or other type ofcommunication technology. In various embodiments, a channel may behosted or provided by a data partner. In various embodiments, thedistribution channel may comprise at least one of a merchant website, asocial media website, affiliate or partner websites, an external vendor,a mobile device communication, social media network and/or locationbased service. Distribution channels may include at least one of amerchant website, a social media site, affiliate or partner websites, anexternal vendor, and a mobile device communication. Examples of socialmedia sites include Facebook®, Foursquare®, Twitter®, MySpace®,LinkedIn®, and the like. Examples of affiliate or partner websitesinclude American Express®, Groupon®, LivingSocial®, and the like.Moreover, examples of mobile device communications include texting,email, and mobile applications for smartphones.

A “consumer profile,” “customer data,” or “consumer profile data” maycomprise any information or data about a consumer that describes anattribute associated with the consumer (e.g., a preference, an interest,demographic information, personally identifying information, and thelike).

In various embodiments, the methods described herein are implementedusing the various particular machines described herein. The methodsdescribed herein may be implemented using the below particular machines,and those hereinafter developed, in any suitable combination, as wouldbe appreciated immediately by one skilled in the art. Further, as isunambiguous from this disclosure, the methods described herein mayresult in various transformations of certain articles.

For the sake of brevity, conventional data networking, applicationdevelopment and other functional aspects of the systems (and componentsof the individual operating components of the systems) may not bedescribed in detail herein. Furthermore, the connecting lines shown inthe various figures contained herein are intended to represent exemplaryfunctional relationships and/or physical couplings between the variouselements. It should be noted that many alternative or additionalfunctional relationships or physical connections may be present in apractical system.

The various system components discussed herein may include one or moreof the following: a host server or other computing systems including aprocessor for processing digital data; a memory coupled to the processorfor storing digital data; an input digitizer coupled to the processorfor inputting digital data; an application program stored in the memoryand accessible by the processor for directing processing of digital databy the processor; a display device coupled to the processor and memoryfor displaying information derived from digital data processed by theprocessor; and a plurality of databases. Various databases used hereinmay include: client data; merchant data; financial institution data;and/or like data useful in the operation of the system. As those skilledin the art will appreciate, user computer may include an operatingsystem (e.g., Windows NT®, Windows 95/98/2000®, Windows XP®, WindowsVista®, Windows 7®, OS2, UNIX®, Linux®, Solaris®, MacOS, etc.) as wellas various conventional support software and drivers typicallyassociated with computers.

The present system or any part(s) or function(s) thereof may beimplemented using hardware, software or a combination thereof and may beimplemented in one or more computer systems or other processing systems.However, the manipulations performed by embodiments were often referredto in terms, such as matching or selecting, which are commonlyassociated with mental operations performed by a human operator. No suchcapability of a human operator is necessary, or desirable in most cases,in any of the operations described herein. Rather, the operations may bemachine operations. Useful machines for performing the variousembodiments include general purpose digital computers or similardevices.

In fact, in various embodiments, the embodiments are directed toward oneor more computer systems capable of carrying out the functionalitydescribed herein. The computer system includes one or more processors,such as processor. The processor is connected to a communicationinfrastructure (e.g., a communications bus, cross over bar, or network).Various software embodiments are described in terms of this exemplarycomputer system. After reading this description, it will become apparentto a person skilled in the relevant art(s) how to implement variousembodiments using other computer systems and/or architectures. Computersystem can include a display interface that forwards graphics, text, andother data from the communication infrastructure (or from a frame buffernot shown) for display on a display unit.

Computer system also includes a main memory, such as for example randomaccess memory (RAM), and may also include a secondary memory. Thesecondary memory may include, for example, a hard disk drive and/or aremovable storage drive, representing a floppy disk drive, a magnetictape drive, an optical disk drive, etc. The removable storage drivereads from and/or writes to a removable storage unit in a well-knownmanner. Removable storage unit represents a floppy disk, magnetic tape,optical disk, etc. which is read by and written to by removable storagedrive. As will be appreciated, the removable storage unit includes acomputer usable storage medium having stored therein computer softwareand/or data.

In various embodiments, secondary memory may include other similardevices for allowing computer programs or other instructions to beloaded into computer system. Such devices may include, for example, aremovable storage unit and an interface. Examples of such may include aprogram cartridge and cartridge interface (such as that found in videogame devices), a removable memory chip (such as an erasable programmableread only memory (EPROM), or programmable read only memory (PROM)) andassociated socket, and other removable storage units and interfaces,which allow software and data to be transferred from the removablestorage unit to computer system.

Computer system may also include a communications interface.Communications interface allows software and data to be transferredbetween computer system and external devices. Examples of communicationsinterface may include a modem, a network interface (such as an Ethernetcard), a communications port, a Personal Computer Memory CardInternational Association (PCMCIA) slot and card, etc. Software and datatransferred via communications interface are in the form of signalswhich may be electronic, electromagnetic, and optical or other signalscapable of being received by communications interface. These signals areprovided to communications interface via a communications path (e.g.,channel). This channel carries signals and may be implemented usingwire, cable, fiber optics, a telephone line, a cellular link, a radiofrequency (RF) link, wireless and other communications channels.

The terms “computer program medium” and “computer usable medium” and“computer readable medium” are used to generally refer to media such asremovable storage drive and a hard disk installed in hard disk drive.These computer program products provide software to computer system.

Computer programs (also referred to as computer control logic) arestored in main memory and/or secondary memory. Computer programs mayalso be received via communications interface. Such computer programs,when executed, enable the computer system to perform the features asdiscussed herein. In particular, the computer programs, when executed,enable the processor to perform the features of various embodiments.Accordingly, such computer programs represent controllers of thecomputer system.

In various embodiments, software may be stored in a computer programproduct and loaded into computer system using removable storage drive,hard disk drive or communications interface. The control logic(software), when executed by the processor, causes the processor toperform the functions of various embodiments as described herein. Invarious embodiments, hardware components such as application specificintegrated circuits (ASICs). Implementation of the hardware statemachine so as to perform the functions described herein will be apparentto persons skilled in the relevant art(s).

The various system components may be independently, separately orcollectively suitably coupled to the network via data links whichincludes, for example, a connection to an Internet Service Provider(ISP) over the local loop as is typically used in connection withstandard modem communication, cable modem, Dish Networks®, ISDN, DigitalSubscriber Line (DSL), or various wireless communication methods, see,e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which ishereby incorporated by reference. It is noted that the network may beimplemented as other types of networks, such as an interactivetelevision (ITV) network. Moreover, the system contemplates the use,sale or distribution of any goods, services or information over anynetwork having similar functionality described herein.

“Cloud” or “Cloud computing” includes a model for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. Cloud computing may includelocation-independent computing, whereby shared servers provideresources, software, and data to computers and other devices on demand.For more information regarding cloud computing, see the NIST's (NationalInstitute of Standards and Technology) definition of cloud computing athttp://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf (lastvisited June 2012), which is hereby incorporated by reference in itsentirety.

As used herein, “transmit” may include sending electronic data from onesystem component to another over a network connection. Additionally, asused herein, “data” may include encompassing information such ascommands, queries, files, data for storage, and the like in digital orany other form.

The computers discussed herein may provide a suitable website or otherInternet-based graphical user interface which is accessible by users. Inone embodiment, the Microsoft Internet Information Server (IIS),Microsoft Transaction Server (MTS), and Microsoft SQL Server, are usedin conjunction with the Microsoft operating system, Microsoft NT webserver software, a Microsoft SQL Server database system, and a MicrosoftCommerce Server. Additionally, components such as Access or MicrosoftSQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be usedto provide an Active Data Object (ADO) compliant database managementsystem. In one embodiment, the Apache web server is used in conjunctionwith a Linux operating system, a MySQL database, and the Perl, PHP,and/or Python programming languages.

Any of the communications, inputs, storage, databases or displaysdiscussed herein may be facilitated through a website having web pages.The term “web page” as it is used herein is not meant to limit the typeof documents and applications that might be used to interact with theuser. For example, a typical website might include, in addition tostandard HTML documents, various forms, Java applets, JavaScript, activeserver pages (ASP), common gateway interface scripts (CGI), extensiblemarkup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX(Asynchronous Javascript And XML), helper applications, plug-ins, andthe like. A server may include a web service that receives a requestfrom a web server, the request including a URL(http://yahoo.com/stockquotes/ge) and an IP address (123.56.789.234).The web server retrieves the appropriate web pages and sends the data orapplications for the web pages to the IP address. Web services areapplications that are capable of interacting with other applicationsover a communications means, such as the internet. Web services aretypically based on standards or protocols such as XML, SOAP, AJAX, WSDLand UDDI. Web services methods are well known in the art, and arecovered in many standard texts. See, e.g., ALEX NGHIEM, IT WEB SERVICES:A ROADMAP FOR THE ENTERPRISE (2003), hereby incorporated by reference.

Practitioners will also appreciate that there are a number of methodsfor displaying data within a browser-based document. Data may berepresented as standard text or within a fixed list, scrollable list,drop-down list, editable text field, fixed text field, pop-up window,and the like. Likewise, there are a number of methods available formodifying data in a web page such as, for example, free text entry usinga keyboard, selection of menu items, check boxes, option boxes, and thelike.

The system and method may be described herein in terms of functionalblock components, screen shots, optional selections and variousprocessing steps. It should be appreciated that such functional blocksmay be realized by any number of hardware and/or software componentsconfigured to perform the specified functions. For example, the systemmay employ various integrated circuit components, e.g., memory elements,processing elements, logic elements, look-up tables, and the like, whichmay carry out a variety of functions under the control of one or moremicroprocessors or other control devices. Similarly, the softwareelements of the system may be implemented with any programming orscripting language such as C, C++, C#, Java, JavaScript, VBScript,Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly,PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, anyUNIX shell script, and extensible markup language (XML) with the variousalgorithms being implemented with any combination of data structures,objects, processes, routines or other programming elements. Further, itshould be noted that the system may employ any number of conventionaltechniques for data transmission, signaling, data processing, networkcontrol, and the like. Still further, the system could be used to detector prevent security issues with a client-side scripting language, suchas JavaScript, VBScript or the like. For a basic introduction ofcryptography and network security, see any of the following references:(1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,”by Bruce Schneier, published by John Wiley & Sons (second edition,1995); (2) “Java Cryptography” by Jonathan Knudson, published byO'Reilly & Associates (1998); (3) “Cryptography & Network Security:Principles & Practice” by William Stallings, published by Prentice Hall;all of which are hereby incorporated by reference.

As will be appreciated by one of ordinary skill in the art, the systemmay be embodied as a customization of an existing system, an add-onproduct, a processing apparatus executing upgraded software, astandalone system, a distributed system, a method, a data processingsystem, a device for data processing, and/or a computer program product.Accordingly, any portion of the system or a module may take the form ofa processing apparatus executing code, an internet based embodiment, anentirely hardware embodiment, or an embodiment combining aspects of theinternet, software and hardware. Furthermore, the system may take theform of a computer program product on a computer-readable storage mediumhaving computer-readable program code means embodied in the storagemedium. Any suitable computer-readable storage medium may be utilized,including hard disks, CD-ROM, optical storage devices, magnetic storagedevices, and/or the like.

The system and method is described herein with reference to screenshots, block diagrams and flowchart illustrations of methods, apparatus(e.g., systems), and computer program products according to variousembodiments. It will be understood that each functional block of theblock diagrams and the flowchart illustrations, and combinations offunctional blocks in the block diagrams and flowchart illustrations,respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Further, illustrations ofthe process flows and the descriptions thereof may make reference touser windows, webpages, websites, web forms, prompts, etc. Practitionerswill appreciate that the illustrated steps described herein may comprisein any number of configurations including the use of windows, webpages,web forms, popup windows, prompts and the like. It should be furtherappreciated that the multiple steps as illustrated and described may becombined into single webpages and/or windows but have been expanded forthe sake of simplicity. In other cases, steps illustrated and describedas single process steps may be separated into multiple webpages and/orwindows but have been combined for simplicity.

The term “non-transitory” is to be understood to remove only propagatingtransitory signals per se from the claim scope and does not relinquishrights to all standard computer-readable media that are not onlypropagating transitory signals per se. Stated another way, the meaningof the term “non-transitory computer-readable medium” and“non-transitory computer-readable storage medium” should be construed toexclude only those types of transitory computer-readable media whichwere found in In Re Nuijten to fall outside the scope of patentablesubject matter under 35 U.S.C. §101.

Systems, methods and computer program products are provided. In thedetailed description herein, references to “various embodiments”, “oneembodiment”, “an embodiment”, “an example embodiment”, etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments.

Benefits, other advantages, and solutions to problems have beendescribed herein with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any elements that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures or elements of the disclosure. The scope of the disclosure isaccordingly to be limited by nothing other than the appended claims, inwhich reference to an element in the singular is not intended to mean“one and only one” unless explicitly so stated, but rather “one ormore.” Moreover, where a phrase similar to ‘at least one of A, B, and C’or ‘at least one of A, B, or C’ is used in the claims or specification,it is intended that the phrase be interpreted to mean that A alone maybe present in an embodiment, B alone may be present in an embodiment, Calone may be present in an embodiment, or that any combination of theelements A, B and C may be present in a single embodiment; for example,A and B, A and C, B and C, or A and B and C. Although the disclosureincludes a method, it is contemplated that it may be embodied ascomputer program instructions on a tangible computer-readable carrier,such as a magnetic or optical memory or a magnetic or optical disk. Allstructural, chemical, and functional equivalents to the elements of theabove-described exemplary embodiments that are known to those ofordinary skill in the art are expressly incorporated herein by referenceand are intended to be encompassed by the present claims. Moreover, itis not necessary for a device or method to address each and everyproblem sought to be solved by the present disclosure, for it to beencompassed by the present claims.

Furthermore, no element, component, or method step in the presentdisclosure is intended to be dedicated to the public regardless ofwhether the element, component, or method step is explicitly recited inthe claims. No claim element herein is to be construed under theprovisions of 35 U.S.C. 112 (f) unless the element is expressly recitedusing the phrase “means for.” As used herein, the terms “comprises”,“comprising”, or any other variation thereof, are intended to cover anon-exclusive inclusion, such that a process, method, article, orapparatus that comprises a list of elements does not include only thoseelements but may include other elements not expressly listed or inherentto such process, method, article, or apparatus.

What is claimed is:
 1. A method comprising: receiving, by a web browser,a navigation command from a merchant server directing the web browser tonavigate to a merchant check out page; receiving, by the web browser,the merchant check out page comprising returned webpage content; andinstantiating, by the web browser, a service call comprising a portionof the returned webpage content, wherein the service call is configuredto be transmitted to a transaction account provider server.
 2. Themethod according to claim 1, wherein the merchant check out page furthercomprises: a digital signature signed on a current timestamp using amerchant SSL certificate private key; and personally identifiableinformation receiver fields of the merchant check out page.
 3. Themethod according to claim 1, wherein the service call comprises asecured CORS HTTPS RESTful service call.
 4. A method according to claim1, wherein the service call comprising a portion of returned webpagecontent is configured to be received by the transaction account providerserver, wherein an originating domain of returned webpage content isconfigured to be validated by the transaction account provider server,wherein a time stamp of the returned webpage content is configured to becompared against a time constraint by the transaction account providerserver, wherein a dynamic banner is configured to be prepared inresponse to the validating by the transaction account provider server,and wherein the dynamic banner is configured to be transmitted by thetransaction account provider server.
 5. The method according to claim 4,wherein a digital signature of the merchant is configured to bevalidated by the transaction account provider server.
 6. The methodaccording to claim 4, wherein a banner request ID of the returnedwebpage content is configured to be validated by the transaction accountprovider server.
 7. The method according to claim 6, wherein the bannerrequest ID uniquely identifies a request for the dynamic banner.
 8. Themethod according to claim 4, wherein the returned webpage contentcomprises a merchant-id.
 9. The method according to claim 4, wherein thedynamic banner comprises at least one of an iFrame configured to host alanding page URL, a browser tab configured to host a landing page URL,and a browser window configured to host a landing page URL.
 10. Themethod according to claim 9, wherein the dynamic banner furthercomprises a secure banner token with an expiration data.
 11. The methodaccording to claim 9, wherein the dynamic banner further comprises asecure URL linked to a portion of the dynamic banner configured toaccept a user interaction.
 12. A customer application method comprising:receiving, by a transaction account provider server, an instruction tothe transaction account provider server from a web browser to open alanding page within the web browser; validating, by the transactionaccount provider server, a secure URL linked to a portion of a dynamicbanner corresponding to a user-banner interaction; opening, by thetransaction account provider server, the landing page within the webbrowser in response to the validating; and wherein the landing page isconfigured to transmit a cross document message to a merchant check outpage.
 13. The customer application method of claim 12, wherein theinstruction to the transaction account provider server from the webbrowser to open the landing page within a web page further comprises aninstruction to open the landing page within an iFrame.
 14. The customerapplication method of claim 12, wherein the validating step furthercomprises validating, by the transaction account provider server, asecure banner token.
 15. The customer application method of claim 12,wherein the landing page is configured to close in response to a crossdocument message from a merchant server.
 16. A method of IAN to checkoutreturn comprising: receiving, by a web browser from a transactionaccount provider server, an IAN details; transmitting, by the webbrowser, a cross document message comprising the IAN details to amerchant page; and pre-filling a purchase payment information inresponse to the IAN details by the merchant page into a shopping cardexperience of the web browser.
 17. The method of IAN to checkout returnaccording to claim 16, wherein the IAN details are displayed by the webbrowser in an iFrame.
 18. The method of IAN to checkout return accordingto claim 16, wherein the web browser forwards the IAN details to amerchant server to complete a transaction.
 19. The method of IAN tocheckout return according to claim 16, wherein the IAN details areprovided in a format comprising an encrypted variable encrypted using apublic key of a merchant server.
 20. The method of IAN to checkoutreturn according to claim 19, wherein the merchant server is configuredto decrypt the IAN details with a private key of the merchant server.